build(deps): bump nanoid from 3.2.0 to 3.3.8 #6988
Conversation
jdstrand
force-pushed
the
jdstrand/update-nanoid
branch
from
0adc5d0 to
4434ae9
Compare
|
@jdstrand It looks like this is failing on a test that shouldn't exist anymore: a test for the C2 subscriptions feature. Let me look into how that's still in there - I had thought those tests were ripped out. |
The tests were indeed ripped out in September, so there is no reason they should be used here. I am re-running it to replicate, but this could be a caching issue on one of the self hosted runners -- not sure. If so, I can ask TKY for the IPs to go in manually and clear the caches. |
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
|
Not sure what was going on with the use of the old subscriptions test, it looks like this was just scriptQueryBuilder flake. |
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
This fixes
nanoidmore completely for https://github.com/influxdata/ui/security/dependabot/100. #6986 updated yarn.lock for thedependencies. This updates package.json so thatdependencieswill correctly contain 3.3.8 instead of 3.2.0 (but yarn.lock stays the same for this resolution) and updatesresolutionsto use 3.3.8 for 3.3.3 in themochadevDependency.In terms of runtime effects, there are no changes for prod and we now use 3.3.8 for the
mochadevDependency.Closes https://github.com/influxdata/idpe/issues/19022